User intent during object scrolling

ABSTRACT

Particular embodiments arrange a plurality of objects in a hierarchy, the hierarchy having one or more layers and each layer having at least one of the objects; display a portion of a sequence of first objects on a screen of a user device, the sequence of first objects all belong to a first layer in the hierarchy, each first object having as its children one or more second objects belonging to a second layer immediately below the first layer in the hierarchy; in response to a user scrolling through the sequence of first objects, estimate which specific first object in the sequence the user is likely to be viewing at a predetermined time in the future based on an acceleration of the user scrolling through the sequence of first objects; and preload the second objects that are children of the specific first object.

RELATED APPLICATION

This application claims the benefit, under 35 U.S.C. §119(e), of U.S.Provisional Patent Application No. 61/593,841, filed on 1 Feb. 2012,which is incorporated herein by reference in its entirety and for allpurposes.

TECHNICAL FIELD

This disclosure generally relates to presenting multimedia objects, suchas images or videos, in a user interface.

BACKGROUND

A user interface (UI), in the industrial design field of human-machineinteraction, is the space where interactions between humans and machinesoccur. The goal of interactions between a human, often referred to as a“user”, and a machine at the user interface is user's control of themachine and its operations (e.g., through user input) and machinefeedback (e.g., through program output). A graphical user interface(GUI) is a type of user interface that allows users to interact withsoftware applications executing on electronic or computing devicesthrough multimedia objects (e.g., images, videos, audios, etc.) ratherthan purely text commands.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a portion of an example object hierarchy.

FIGS. 2A-2D illustrate an example of simulating a 3D object on a 2Dmedium.

FIGS. 3A-3C illustrate an example of simulating a 3D object on a 2Dmedium.

FIG. 4 illustrates an example of simulating a 3D object on a 2D medium.

FIGS. 5A-5B illustrate an example of simulating a light source in avirtual 3D space.

FIG. 6 illustrates an example series of pages in an electronic book.

FIGS. 7A-7D illustrate an example of previewing objects arranged in aseries.

FIGS. 8A-8B illustrate an example of scrolling through a series ofobjects.

FIGS. 9A-9C illustrate an example of scrolling through objects in ahierarchy.

FIG. 10 illustrates an example electronic device.

DESCRIPTION OF EXAMPLE EMBODIMENTS

In particular embodiments, a user interface (UI), and more specifically,a graphical user interface (GUI) may include any number of UI componentsor elements arranged in a hierarchy. The components of a user interfacemay be presented to users according to the hierarchical structure. Inparticular embodiments, some of these UI components may correspond to orrepresent multimedia objects, such as images, videos, or audios.Sometimes, these multimedia UI components may be presented to usersindividually on their own. Other times, they may be presented to userswhile contained in other UI components, such as being included in awindow, a panel, or a web page. In particular embodiments, there may bemultiple presentations modes for presenting images or videos in a userinterface.

In particular embodiments, a user may interact with a multimedia UIcomponent using a suitable input device (e.g., a finger or stylus on atouch-sensitive screen or a mouse). For example, the user may play orpause a video, or zoom or pan or rotate an image. In particularembodiments, depending on how or where a multimedia UI component ispresented to a user (e.g., which presentation mode it is in), the user'sinteraction with the multimedia UI component may result in differentbehaviors from the multimedia UI component.

Object Hierarchy

In particular embodiments, objects may be organized into a hierarchy.For example, objects may be organized into a hierarchy based on how theindividual objects are related to each other. The object hierarchy mayhave any number of levels, and at each level, there may be any number ofobjects. Parent-child or sibling relationships may exist betweenspecific objects in the hierarchy. Within the hierarchy, a parent objectis one level above the level of its child objects. Two sibling objectsare at the same level and share the same parent object. In addition, anyportion of the hierarchy may also be considered a hierarchy in itself.

FIG. 1 illustrates a portion of an example object hierarchy 100 thatincludes a number of objects 110. In particular embodiments, an objectin a hierarchy may or may not have a parent. If an object does not havea parent, it may be referred to as a “root” object (e.g., object 110A).In particular embodiments, an object in a hierarchy may or may not haveany children. If an object does not have any children, it may bereferred to as a “leaf” or “terminal” object (e.g., object 110B). If anobject does have children (e.g., object 110C), it may have any number ofchildren. In addition, objects sharing the same parent may be referredto as each other's “siblings”. For example, in FIG. 1, object 110C isthe parent of objects 110D and 110B. Objects 110D and 110B are thechildren of object 110C and are siblings to each other. Thus, ahierarchy of objects (e.g., object hierarchy 100) not only includes theindividual objects themselves but also indicates the relationships amongthe specific objects. Moreover, the position of a specific object withinthe hierarchy may indicate its relationships with other objects in thehierarchy.

Objects may be of any applicable types. In particular embodiments, anobject may be a component of a user interface. In this case, the objecthierarchy may be a UI hierarchy (e.g., a hierarchy of UI components). Inother words, components of a user interface may be organized into ahierarchy. The UI hierarchy may have any number of layers correspondingto the levels of the object hierarchy, and at each layer, there may beany number of UI components. The position of a specific UI componentwithin the hierarchy may indicate its relationships with other UIcomponents in the hierarchy. The UI components may be presented to usersaccording to the hierarchical structure (e.g., in layers). In particularembodiments, some of these UI components may be multimedia objects, suchas images, videos, or audios.

In particular embodiments, an object may correspond to a piece ofuser-consumable content. In particular embodiments, an object may beconsumed by a user if the user may, for example and without limitation,interact with, view, read, listen to, manipulate, or handle the object.For example, some user-consumable objects may be texts, images, videos,audios, feeds, executables (e.g., application programs or games),websites, web pages, digital books, photo albums, posts, or messages. Inparticular embodiments, user-consumable content, or more specifically,user-consumable objects, may be organized into a hierarchy based on, forexample, the relationships among the individual pieces ofuser-consumable content. Consequently, a hierarchy of user-consumablecontent may be represented as a hierarchy of objects, where individualobjects in the hierarchy may correspond to specific pieces ofuser-consumable content (e.g., texts, images, videos, audios,executables, etc.). In addition, the structure of the hierarchyindicates the relationships among the specific pieces of user-consumablecontent.

In particular embodiments, the relationships among the objects in ahierarchy may correspond to how the objects are organized and presentedto users. In particular embodiments, when presenting a hierarchy ofobjects to a user of a device, the objects may be organized andpresented according to the structure of the object hierarchy. Morespecifically, the objects may be presented in a user interface providedon the device according to the structure of the object hierarchy so thatthe user interface itself becomes hierarchical as well. Consequently,the user interface may include a number of layers, respectivelycorresponding to the levels in the object hierarchy. The positions ofthe objects within the hierarchy are preserved in the user interface,such that a specific object at a specific position in the hierarchy ispresented in the corresponding position in the user interface. Therelationships among the objects within the hierarchy are maintained inthe user interface. In other words, there may be an one-to-onecorrespondence between an object in the object hierarchy and a UIcomponent in the user interface, such that each object is represented bya UI component.

As an example, in the context of the desktop of a computing device, thedesktop may be a parent object, and sometimes the root object of ahierarchy, whose child objects are the individual software applicationsavailable on the desktop. A software application, while itself being oneof the child objects of the desktop, is also the parent object of theindividual components of that software application. Different softwareapplications may include different components. For example, for asoftware application that manages digital books (e.g., a book readerapplication), its components may include the digital books available,the individual chapters of each book, the pages of each chapter, and thetexts, images, videos, audios, or any graphical user interface (GUI) orcontent or media elements on each page. Each of these also correspondsto an object in the hierarchy. More specifically, when these objects areorganized in a hierarchy, the book application may be the parent objectof the digital books. A digital book may be the parent object of theindividual chapters of that book. A chapter, while itself being one ofthe child objects of the book, is also the parent object of the pages inthat chapter. A page is the parent object of the texts, images, videos,audios, or any GUI or content or media elements on that page. A textblock, image, video, audio, or GUI or content or media element is one ofthe child objects of the page to which it belongs. Similarly, for asoftware application that manages news feeds, its components may includethe individual news channels and the news stories within each channel.Each of these may correspond to an object. When these objects arearranged in a hierarchy, the news-feed application, while itself beingone of the child objects of the desktop, is also the parent object ofthe news channels. A news channel in turn is the parent object of thenews stories included in that channel. Some of these objects mayrespectively correspond to UI components of a user interface presentedon the computing device.

As another example, in the context of the Internet or the World WideWeb, the Internet may be a parent object whose child objects are theindividual websites. A website, while itself being one of the childobjects of the Internet, is also the parent object of the individual webpages of that website. A web page, while itself being one of the childobjects of the website to which it belongs, is the parent object of thetexts, images, videos, audios, or links (e.g., Uniform Resource Locators(URLs)) included in the web page. Each text block, image, video, audio,or link may also correspond to a specific object in the hierarchy. Someof these objects may respectively correspond to UI components of aweb-based user interface that may be presented to a user through a webbrowser.

As a third example, a website, such as a social-networking website, mayalso be arranged in such a hierarchical structure for navigating thecontent of the social-networking website. In this context, thesocial-networking website may be a parent object whose child objects arethe components (e.g., photo albums, user profile pages, etc.) of thewebsite. For example, a photo album, while itself being a child objectof the social-networking website, may in turn be a parent object, andthe individual photos within the album may be the child objects of thephoto album. A user's profile page may be structured in such ahierarchical fashion as well. The profile page itself may be considereda parent object, and the individual objects on the profile page may bethe child objects of the profile page. In particular embodiments, aprofile page may be considered and rendered (e.g., for presentation to auser) as a linear timeline of objects, such as, for example and withoutlimitation, photos, photo albums, check-ins, comments from other users,attended events, tags, etc. In particular embodiments, child objects inthe hierarchy may also include applications the user has added to theprofile page, such as a Spotify music sharing application. Moreover,individual stories, songs the user has listened to, and playlists may bechild objects at a lower hierarchical level. In particular embodiments,child objects in the hierarchy may include particular sections of auser's profile, such as the user's education and employment information,or the public “wall” of the user's profile page. This disclosurecontemplates representing and addressing any collection of content in ahierarchical object or nodal structure. Again, these objects mayrespectively correspond to UI components of a web-based user interfacethat may be presented to a user through a web browser.

As these examples illustrate, an object may be of any type and thisdisclosure contemplates any applicable types of objects. For example andwithout limitation, the term “object” may refer to any type of content,including but not limited to images, videos, captions, text blocks orboxes, user interface elements, URLs, newsfeed stories, references toother objects, advertisements, calendar events, units for displayingopen graph analysis that may be graphically rendered, applications,websites, web pages, books, chapters. In particular embodiments, given ahierarchy of objects, which may be a portion of another, largerhierarchy of objects, the hierarchical relationships (e.g., parent-childor sibling relationships, positions of the objects within the hierarchy)between specific objects may direct some aspects of how these objectsbehave in the context of a user interface or how the objects arepresented to a user.

A hierarchy of objects may be displayed in a user interface that has acorresponding hierarchical structure. In particular embodiments, theuser interface may include any number of layers, where each layercorresponds to a specific level of the object hierarchy. In particularembodiments, the lower layers of the user interface correspond to thetop levels of the object hierarchy, while the upper layers of the userinterface correspond to the bottom levels of the object hierarchy. Thatis, an object is displayed at a layer in the user interface that isbelow the layer of its child object and above the layer of its parentobject. Since a child object and a parent object are displayed in twoseparately layers in the user interface, the child object may beconsidered as “floating” on top of its parent object.

In particular embodiments, the user interface may be displayed on thescreen of an electronic device for presentation to users. In particularembodiments, the screen may be touch sensitive and include atouch-sensitive input. A user may interact with various objectsdisplayed on the screen by touching the screen with his fingers.

Shadows Cast by Objects

A display device, such as the screen of an electronic device, is atwo-dimensional (2D) medium. Nevertheless, three-dimensional (3D) effectmay be simulated (e.g., using shadows and perspective techniques) topresent and display an 3D object on such 2D medium, similar to paintinga 3D object on a 2D canvas. In particular embodiments, a 3D virtualworld may be created and 3D objects may be placed in such a virtualworld. Shadows may be cast around an object to simulate the 3D effect.The size, shape, orientation, and color of the shadows may depend on,for example and without limitation, the size, shape, orientation, orcolor of the object, the distance between the object and the lightsource, and the spatial relationship between the object and the lightsource. The objects may be projected and displayed onto a 2D mediumusing applicable perspective techniques.

As an example, FIG. 2A illustrates presenting a 3D object in a userinterface displayed on a 2D medium and using shadows to simulate the 3Deffect. In this case, the user interface is a page 200 of an electronicbook. The page may include texts and other multi-media objects, such asimage, video, clickable URL, and caption. In FIG. 2A, image 210 visuallyfloats on top of page 200, indicating that users may interact with image210 in various manners. In fact, in FIG. 2A, only half of the entireimage 210 (e.g., a cropped version) is actually shown as image 210 laysflat on page 200. A user may “lift” image 210 up and off page 200 bypinching image 210 with two fingers, as illustrated in FIG. 2B. The twofingers may be placed anywhere near one or more edges of image 210. Whenimage 210 is pinched up and off the page, the entire image appears, butfolded at an angle relative to the distance between the two fingers theuser used to pinch the image. If the user pinches out beyond apredetermined threshold distance and then takes his fingers off theimage, the image expands to fill the entire screen. To simulate theeffect of a two-dimensional object (e.g., folded image 210) in athree-dimensional virtual space, shadows are placed around image 210.

In particular embodiments, a light source is simulated to cause theeffect of shadowing around a floating object. A virtual 3D space may beconstructed to encompass the object and the virtual light source. Lightis shone on the object (e.g., image 210), causing shadows to be castaround the object on the background (e.g., page 200).

For example, in the case illustrated in FIG. 2B, a simulated lightsource 250 may be placed in the center of page 200. The shadows aroundimage 210 change depending on the position of image 210 in relation tosimulated light source 250. For example, in FIG. 2C, image 210 is movedtoward the left side of the screen (e.g., near the left edge of page200). In this case, there is more, darker shadow on the left side ofimage 210 and less, lighter shadow on the right side of image 210, asthe left side of image 210 faces away from simulated light source 250and the right side of image 210 faces toward simulated light source 250.In addition, image 210 is rotated more toward the left so that there ismore of the right half of image 210 shown but less of the left half ofimage 210 shown. In contrast, in FIG. 2D, image 210 is moved toward theright side of the screen (e.g., near the right edge of page 200). Inthis case, there is more, darker shadow on the right side of image 210and less, lighter shadow on the left side of image 210, as the rightside of image 210 faces away from simulated light source 250 and theleft side of image 210 faces toward simulated light source 250. Inaddition, image 210 is rotated more toward the right so that there ismore of the left half of image 210 shown but less of the right half ofimage 210 shown. In particular embodiments, when an object (in theexample above, image 210) is manipulated (e.g., moved or rotated), otherobjects, such as text objects, layered below the image is stationary,permitting the user to manipulate the image and read the entire textsimultaneously.

Similar shadowing effect may be applied to an image when the image ispinched up and moved toward the top or bottom of the screen. As anexample, a page 300 illustrated in FIG. 3A includes a floating imageobject 310. In FIG. 3A, again, image 310 is displayed on a page 300 ofan electronic book. In FIG. 3A, image 310 lays flat on page 300 and onlya portion of image 310 is shown. A user may pinch image 310 up with twofingers (e.g., by placing the two fingers near the opposite edges ofimage 310). When this happens, image 310 unfolds partially as describedabove. In FIG. 3B, image 310 is brought near the top of the screen. Atthis position, image 310 is rotated more toward the bottom so that moreof the top half of image 310 is shown, and there is more shadow on thebottom side of image 310 than on the top side of image 310. In thisexample, a simulated light source is placed above page 300. In contrast,in FIG. 3C, image 310 is brought near the bottom of the screen. At thisposition, image 310 is rotated more toward the top so that more of thebottom half of image 310 is shown, and there is more shadow on the topside half of image 310 than on the bottom side of image 310.

When a floating object is pinched up, it may be moved to differentpositions on the screen, as illustrated in FIGS. 2C, 2D, 3B, and 3C. Itmay also be rotated, as illustrated in FIG. 4. Here, an image 410included in a page 400 has been pinched up (e.g., using two fingers) androtated (e.g., by rotating the fingers pinching image 410). The shadowsaround image 410 rotate with image 410 accordingly to maintain thethree-dimensional effect. The shape of the shadows may also be adjustedbased on the current spatial relationships between the object and thelight source. In addition, as illustrated in FIG. 4, a portion of image420 overlays the text behind it on page 400. In particular embodiments,when a floating object (e.g., image or video) overlays some text behindit, the appearance of the text may be adjusted to simulate the effect ofthe shadow casted by the object on the text (e.g., slightly darkened ordistorted). In particular embodiments, when an object is picked up(e.g., pinched with two fingers), its size may change with the movementof the two fingers. By moving the two fingers further apart, the objectmay be enlarged. Conversely, by moving the two fingers closer together,the size of the object may be decreased.

In particular embodiments, when an object is being manipulated by a user(e.g., picked up, rotated, zoomed in or out, etc.), the object itself,not an instance of the object, is manipulated. This ensures theself-consistency of the UI. For example, while a video is being played,the user may manipulate the video object (e.g., pinched down to athumbnail size or pinched up to full screen). While the video object isbeing manipulated by the user, the playback of the video continuesuninterrupted.

In particular embodiments, to simulate the effect of picking up anobject in the three-dimensional virtual space, when an object is pickedup, the object below it is moved backward in the virtualthree-dimensional space. As an example, to simulate the effect of image210 being “picked up” from page 200, the size of image 210 (i.e.,object) may be increased while the size of page 200 (i.e., background)may be decreased so that it appears as if image 210 is moving closer tothe user. As another example, when image 410 is pinched up, page 400 ismoved backward to create the visual effect of a greater distance betweenimage 410 and page 400, which in turn simulates the effect of image 410being picked up from page 400. The shadow image 410 casts on page 400increases in size accordingly.

The simulation of the effect of picking up a two-dimensional object in avirtual three-dimensional space is further illustrated in FIGS. 5A-5B.In FIG. 5A, the distance between objects 510 and 520 is D1. A lightsource 530 above object 510 causes object 510 to cast a shadow 541 ofobject 510 onto object 520. In FIG. 5B, object 510 has moved away fromobject 520 and closer to light source 530. The distance between objects510 and 520 is D2, which is greater than D1. Light source 530 againcauses object 510 to cast a shadow 542 of object 510 onto object 520.But because object 510 is now further away from object 520, shadow 542is larger than shadow 541. Thus, by changing the size of the shadow afirst object casts onto a second object, it may stimulate the effectthat the first object is moving away from (e.g., increasing shadow size)or moving closer toward the second object (e.g., decreasing shadowsize).

In particular embodiments, the shadow of an object (e.g., an image) maybe implemented as a separate layer of the user interface. For example,in FIG. 4, image 410 partially overlaps some texts on page 400. There isshadow 420 surrounding image 410. The texts covered by shadow 420 may bedarkened accordingly as well. In some implementations, the shadow aroundan object may be drawn as a blurry dot, sliced up horizontally andvertically, and then stretched up to fill the necessary shadow area.This allows the shadow of an object to be determined without performingray tracing, which is very computationally intensive and thus resourcedemanding.

In particular embodiments, when an object is pinched up with twofingers, the size of the object may change depending on the positions ofthe two fingers. As an example, in FIG. 2B, the two fingers are placednear the opposite edges of image 210. If the two fingers move closertogether, image 210 may fold more so that the two edges of image 210move closer together, following the movement of the two fingers.Conversely, if the two fingers move further apart, image 210 may foldless so that the two edges of image 210 move further apart, againfollowing the movement of the two fingers. The shadows around image 210also move (e.g., expand or contract in size) with the edges of image210, following the movement of the two fingers.

In particular embodiments, to render the shadows around an object in auser interface having a hierarchical structure, the object may berendered on a first layer in the hierarchy while the shadows around theobject may be rendered on a second layer, below the first layer, in thehierarchy. In particular embodiments, to simulate the shadows, a darkpixel (e.g., black or dark grey) may be placed behind the object andnear the center of the object, and the pixel may be enlarged and blurreduntil the pixel extends beyond at least some of the edges of the object.In particular embodiments, the color of the pixel may be a gradient,gradually transitioning from light at the edges of the pixel to dark atthe center of the pixel, as illustrated in FIG. 4.

Previewing Objects Arranged in a Series

Sometimes, a collection of objects may be arranged in a series anddisplayed according to a specific order. Furthermore, due to the sizerestriction of the display device (e.g., a screen of an electronicdevice), one object from the series may be displayed at a time. As anexample, an electronic book may include many pages. A user may read onepage at a time so that one page is displayed on the user's device at atime. Furthermore, the pages are displayed according to a specific order(e.g., the order of the pages in the book). FIG. 6 illustrates a seriesof pages 610 contained in an electronic book. As another example, aphoto album may include many photos. A user may view one photo at a timeso that one photo is displayed on the user's device at a time. Thephotos may be displayed according to a specific order (e.g.,chronological order).

In particular embodiments, the display device may be a touch screendevice. The user may move forward or backward in the series of objectsby swiping fingers across the touch screen (e.g., swiping fingers towardthe left side of the screen moves toward the end of the series andswiping fingers toward the right side of the screen moves toward thebeginning of the series).

In particular embodiments, when an object in a series is displayed onthe screen, the user may preview the object immediately before or afterthat object in the series. The object currently being displayed may bereferred to as the “current object”. As an example, suppose that thepages of an electronic book are displayed one page at a time. In FIG.7A, a specific page 750 from the book is currently displayed, andcurrent page 750 occupies the entire display screen.

If the user wishes to preview the page immediately after page 750, theuser may swipe his fingers across the screen toward the left side of thescreen. This may cause page 750 to move toward the left side of thescreen corresponding to the movement of the user's fingers. In FIG. 7B,a portion of page 750 has moved off the left edge of the screen. Theremaining portion of page 750 now only occupiers a portion of thedisplay screen (on the left side of the screen). At the same time, aportion of page 760, which is the page immediately after page 750, hasmoved onto the screen and is displayed immediately next to and afterpage 750, in the available portion on the right side of the displayscreen. The user may now preview page 760. In particular embodiments,page 760 is displayed in a size smaller than that of page 750. Thisvisually indicates to the user that page 750 is still the current page.In addition, in particular embodiments, a shadow 762 is displayed aroundpage 760 (i.e., the page being previewed). Alternatively, page 760 maybe slightly dimmed. This helps the user avoid claustrophobia.

If the user wishes to preview the page immediately before page 750, theuser may swipe his fingers across the screen toward the right side ofthe screen. This may cause page 750 to move toward the right side of thescreen corresponding to the movement of the user's fingers. In FIG. 7C,a portion of page 750 has moved off the right edge of the screen. Theremaining portion of page 750 now only occupiers a portion of thedisplay screen (on the right side of the screen). At the same time, aportion of page 740, which is the page immediately before page 750, hasmoved onto the screen and is displayed immediately next to and beforepage 750, in the available portion on the left side of the displayscreen. The user may now preview page 740. In particular embodiments,again, page 740 is displayed in a size smaller than that of page 750.This visually indicates to the user that page 750 is still the currentpage. In addition, in particular embodiments, a shadow 742 is displayedaround page 740 (i.e., the page being previewed). Alternatively, page740 may be slightly dimmed. This helps the user avoid claustrophobia.

The amount of displacement for page 750 may correspond to the amount ofmovements of the user's fingers. The speed of the pages' movements maybe the same as the speed of the user's fingers' movements. In particularembodiments, if the user's fingers move across the screen for a distanceless than a threshold (e.g., half of the width of the screen), then thepage immediately before or after the currently displayed page is shownin its preview mode, as illustrated in FIGS. 7B and 7C. On the otherhand, if the user's fingers move across the screen for a distance morethan a threshold (e.g., half of the width of the screen), then thecurrently displayed page becomes the secondary page and the previewedpage becomes the primary page. For example, in FIG. 7D, the user'sfingers have moved toward the left of the screen sufficiently far suchthat page 750 becomes the secondary page and page 760 (i.e., the pagethat originally being previewed) becomes the primary page. The size ofpage 750 is now smaller than that of page 760. Furthermore, the shadow752 is now around page 750, instead of page 760. At this point, if theuser's fingers continue to move toward the left of the screen,eventually, page 750 shall move off the screen completely and page 760shall move onto the screen completely. Page 760 is then displayed in itsentirety and occupiers the entire screen. Page 760 now becomes thecurrent page.

In particular embodiments, when the user releases the pages by movinghis fingers away from the touch screen, if the user's fingers have movedacross the screen for a distance less than a threshold, then the previewpage is moved off the screen while the current page is moved back intoits original position so that the entire current page is displayed andoccupies the entire screen. On the other hand, if the user's fingershave moved across the screen for a distance more than a threshold, thenthe original current page is moved off the screen. Instead, the originalpreview page is centered on the screen so that the entire preview pageis displayed and occupies the entire screen. At this point, the previewpage becomes the current page. For example, if the user releases thepages in the situation illustrated in FIG. 7C, page 740 (the previewpage) moves off the screen and page 750 returns to its original positionand occupies the entire screen. On the other hand, if the user releasesthe pages in the situation illustrated in FIG. 7D, page 750 moves offthe screen and page 760 (the preview page) moves to the center of thescreen and is displayed in its entirety and occupies the entire screen.Page 760 is now the current page.

Scrolling Through Objects Arranged in a Series

With a collection of objects arranged in a series and displayedaccording to a specific order, sometimes, the user may also scrollthrough the objects. Again, the user may swipe his fingers across thescreen to move forward or backward along the series. For example, toscroll forward along the series, the user may swipe his fingers towardthe left or up side of the screen. Conversely, to scroll backward alongthe series, the user may swipe his fingers toward the right or down sideof the screen.

When the user is scrolling through a series of objects, at any giventime, a portion of the series may be displayed on the screen. Forexample, an electronic book may include a series of pages, and the usermay scroll through these pages. At a particular time, only a few pagesin the book are displayed on the screen. An album may include a seriesof images, and the user may scroll through these images. At a particulartime, only a few images in the album are displayed on the screen. Asillustrated in FIG. 8A, objects 810, 820, 830, 840, and 850, which maybelong to a series of objects (e.g., pages or images) that include otheradditional objects, may be displayed on the screen at a particular time.Due to the size limitation of the screen, a portion of objects 810 and850 are cut off at the edge because these two objects are respectivelypositioned near the left and right sides of the screen and cannot be fitonto the screen completely.

While the user is looking at the objects displayed on the screen at anygiven time, the user may focus his attention more on the object near thecenter of the screen. In particular embodiments, the object near thecenter of the screen (e.g., object 830) may be visually embellished sothat it stands out more to the user.

For example, as illustrated in FIG. 8A, object 830 is currently near thecenter of the screen. Object 830 may be displayed at a size somewhatlarger than the other objects 810, 820, 840, 850. There may be aboundary around each object, and the boundary of object 830 currentlynear the center of the screen may slightly overlap or be on top ofobjects 820 and 840 positioned immediate to the left and right of object830. In addition, there may be a shadow around object 830. Thisdisclosure contemplates any applicable visual embellishment for object830 in order to make it stand out more to the user. In particularembodiments, to make object 830 near the center of the screen stand out,the two objects next to it (i.e., objects 820 and 840) may be slightlydarkened.

In particular embodiments, the screen may be touch sensitive. The usermay swipe his fingers across the screen to scroll through the series ofobjects. Suppose that the user swipes his fingers toward the left sideof the screen so that the user is scrolling toward the back of theseries. In this case, objects 810, 820, 830, 840, and 850 may graduallymove toward the left (e.g., at the same speed as the user's fingers). Asillustrated in FIG. 8B, object 810 may move completely off the screenwhile object 850 may move completely onto the screen. The objectimmediately following object 850 in the series (i.e., object 860) maygradually become visible. Further more, object 830 is no longer near thecenter of the screen. Instead, object 840 is now near the center of thescreen.

In particular embodiments, the visual embellishment for object 830 maybe removed as it is no longer near the center of the screen. Object 830is now displayed at the same size as the other objects and there is noshadow around object 830. On the other hand, visual embellishment, suchas larger size and shadow, may be applied to object 840 to make it standout more as it is now near the center of the screen.

In particular embodiments, as the user scroll through a series ofobjects, at any given time, a portion of the series is displayed on thescreen. The particular object that is currently near the center of thescreen is visually embellished so that it stands out more. As eachobject moves near the center of the screen, visually embellishment isapplied to that object. As each object moves away from the center of thescreen, visual embellishment is removed for that object.

In particular embodiments, objects may be arranged in a hierarchy anddisplayed in a user interface that has a corresponding hierarchicalstructure. For example, components of an electronic book may be arrangedand displayed hierarchically. The book itself may be at the top level ofthe hierarchy. The second level may be the individual sections of thebook. The third level may be the individual pages of the book. Each pageis the child of the section to which it belongs, and each section is theparent of all the pages in that section.

When such a book is displayed in a hierarchical user interface, therelationships between the sections and the pages may be maintained. Forexample, all the sections may form a series of objects, while all thepages may form another series of objects. The sections may be displayedin one layer of the user interface, while the pages may be displayed inanother layer, above the section layer, of the user interface. The usermay scroll either the sections or the pages.

In particular embodiments, when the user scrolls through the sections,as the scrolling moves from one section to another section, the pagesmay be automatically advanced, such that when the user is currentlyviewing the first section, the pages in the first section are displayed,but when the user is currently viewing the second section, the pages inthe second section are displayed. On the other hand, when the userscrolls through the pages, as the scrolling moves from pages of oneaction to pages of another section, the sections may be automaticallyadvanced, such that when the user is currently viewing the pages of thefirst section, the first section is displayed, but when the user iscurrently viewing the pages of the second section, the second section isdisplayed.

To further explain this scrolling process, suppose that a user has movedto a specific section of the book by sliding a finger in the leftdirection across the screen of the electronic device. FIG. 9Aillustrates a section (e.g., the “Introduction” section) of the book. Inthis view, the first or title page 930A of the section is used as thebackground 910 for the entire section. Near the bottom of the screen isa table of contents (TOC) area 920. TOC area 920 includes the individualpages 930 of the current section, shown in thumbnail format and arrangedhorizontally across the screen of the electronic device. In particularembodiments, each page thumbnail is implemented as an object floating onan imaginary or metaphorical “strip” of paper. The metaphor of objectsfloating on a strip of paper reflects the nodal hierarchical structureof each section. The background page represents a chapter/section (theparent object), whereas each of the floating objects in the TOC strip isa child object. This disclosure contemplates extension of this conceptto any collection of content organized in a hierarchical structure.Thus, a photo album having the aforementioned nodal structure may berendered as a film strip (parent object) including floating photothumbnails for each photo contained in the album (child objects). Asanother example, a user profile or timeline may be represented as aninfinite imaginary strip of paper (the parent object) containing aplurality of floating thumbnails representing photo albums,applications, events, etc. (child objects), each of which may containits own child objects.

FIG. 9A illustrates a layered arrangement of objects corresponding to anobject hierarchy. In this case, background area 910 is the bottom layer.TOC area 920 is another layer positioned on top of the background layer.Pages 930 are a third layer positioned on top of the TOC layer. In anobject hierarchy, the background may be the parent of the TOC, and theTOC may be the parent of the pages.

A user may move forward and backward to different pages in the sectionby sliding a finger in the left or right directions, respectively,across TOC area 920. Suppose that a user has slide a finger in the leftdirection across TOC area 920. In FIG. 9B, more pages (e.g., pages 930F,930G, 930H) of the current “Introduction” section appears in TOC area920.

Similarly, a user may move forward and backward to different sections inthe book by sliding a finger in the left or right directions,respectively, either across background area 910 or across TOC area 920.When the user slides a finger across TOC area 920, the current sectionswitches to the next section when the user reaches the last page of thecurrent section; or the current section switches to the previous sectionwhen the user reaches the first page of the current section. FIG. 9Cillustrates the transition between the “Introduction” section and“Chapter 1” of the book. Here, the “Introduction” section is currentlybeing viewed, and “Chapter 1” is the section that immediately followsthe “Introduction” section in the book. In one situation, as a user'sfinger slides in the left direction across TOC area 920, eventually thelast page of the “Introduction” section is reached. At this point, titlepage 930A of the “introduction” section displayed in background area 910gradually moves left out of view, in synchronization with the movementof the last few pages of the “Introduction” section. At the same time,the tile page 940A of “Chapter 1” gradually moves left into view to bedisplayed in background area 910, also in synchronization with themovement of the first few pages of “Chapter 1”. Eventually, title page940A of “Chapter 1” replaces title page 930A of the “Introduction”section when “Chapter 1” becomes the current section being viewed by theuser. In another situation, as a user's finger slides in the leftdirection across background area 910, title page 930A of the“Introduction” section gradually moves left out of view, following bytitle page 940A of “Chapter 1”, which gradually moves left into view tobe displayed in background area 910, effectively replacing title page930A of the “Introduction” section. In synchronization with the movementof title pages 930A and 940A, the last few pages of the “Introduction”section gradually move left out of view and the first few pages of“Chapter 1” gradually move left into view in TOC area 920. Asillustrated in FIG. 9C, at the point of transition 950 between the twosections, the right or left edge of the title page in background area910 lines up with the right or left edge of the last or first page,respectively, of the corresponding section in TOC area 920. Thetransition between a current section and a section immediately beforethe current section behaves similarly, with the exception that insteadof moving in the left direction across the screen of the electronicdevice, objects move in the right direction.

User Intent During Scrolling

When the user is scrolling through objects in a hierarchy, as the user'sfingers swipe across the screen, particular embodiments may estimatewhich specific object the user will view at a predetermined time in thefuture (e.g., 0.2 seconds in the future) based on the velocity oracceleration of the finger movements. For example, as the user isscrolling through a series of sections in a book, where each section mayinclude a number of pages, particular embodiments may estimate whichsection the user will view 0.5 seconds in the future. As the user isscrolling through a series of photo albums, where each album may includea number of photos, particular embodiments may estimate which album theuser will view 0.4 seconds in the future. This may enable the device topreload (e.g., download or render) the pages in that section or thephotos in that album so that when the user is ready to view the pages orphotos, they are already available and ready. In other words, as theuser is scrolling through objects at a specific level of the hierarchy,particular embodiments may estimate which object the user will view at apredetermined time in the future. Then the child objects of that objectmay be preloaded so that they are ready for the user. For example, thechild objects may be downloaded from a server or rendered on the user'sdevice.

In particular embodiments, as the user swipes his fingers across thescreen to scroll through a series of object, the velocity of the fingermovements may be detected. The acceleration of the finger movements maybe computed based on the velocity. The estimation may be based on theacceleration. For example, higher acceleration may suggest that the userwill view an object further away from the object currently beingdisplayed on the screen while lower acceleration may suggest that theuser will view an object closer to the object currently being displayedon the screen at the predetermined time in the future.

In particular embodiments, the vector of the user's touch input, or itsderivative vector, may be utilized to ascertain whether a user wishes tobrowse other objects on the same hierarchical level as the currentobject, or the child objects of the current object. For example, if auser is swiping through a series of photo album objects on a profilepage in a social networking website, the touch input vector may have ahigh velocity, or, even more tellingly, a high acceleration. Such aninput may signal to the application that the user wishes to browse otherphoto albums, and the application may begin downloading photo albumthumbnails based on the magnitude of acceleration or velocity of theinput vector. For example, if a user swipes from the ith album at a highvelocity or acceleration, the application may load thumbnails for the(i+10)th album, whereas if a user swipes slowly from the ith album, theapplication may load thumbnails for the (i+1)th album. Conversely, ifthere is no velocity or acceleration to the input vector (i.e., noswiping input), the application may begin to download the child objects(individual photos) of the currently viewed album cover. In the contextof a digital book, content elements may be pre-drawn and loaded into abuffer based on where the user has scrolled; the digital bookapplication extrapolates from the user's screen size to determine thesize and contents of the buffer.

Spring Motions During Object Animation

In particular embodiments, movements of an object displayed in a userinterface on a screen may be simulated based on spring movement. As theuser interacts with the object, the object may move around the screen.This may be shown as animated sequences depicting the object'smovements. For example, as the user picks up an object by pinching theobject with two fingers, the object may move with the user's fingers. Ifthe use releases the object, the object may return to its originalposition. The user may throw the object against the edge of the screen,causing the object to bounce around the screen.

In particular embodiments, movements of the object may be simulated byattaching one end of a virtual spring to the object and another end ofthe virtual spring to a position on the screen (e.g., the originalposition of the object, the center of the screen, a corner of thescreen, or an edge of the screen). Any number of virtual springs may beattached to an object. In particular embodiments, the movements of theobject may be determined based on Hooke's law: F=−kx; where x is thedisplacement of the spring's end from it's equilibrium position (e.g., adistance, in SI units: meters), F is the restoring force exerted by thespring on that end (in SI units: N or kg·m/s²), and k is a constantcalled the rate or spring constant (in SI units: N/m or kg/s²). Whenthis equation holds, the behavior is said to be linear. The negativesign on the right hand side of the equation is there because therestoring force always acts in the opposite direction of thedisplacement (e.g., when a spring is stretched to the left, it pullsback to the right). In general, the following properties are involved indetermining spring movement: mass, damping, spring stiffness, springrest length. In some implementations, a virtual mass may be assigned tothe object.

In particular embodiments, a virtual spring may have different statevalues based on what the user is doing (e.g., how the user isinteracting with the object). The spring may ramp from one set of statevalue to another, instead of cutting, to make animation sequence of theobject's movements appear more natural. For example the distance betweenan edge of the object and the user's finger on the object may be used todetermine the tightening of the springs used in the animation or thelevel of ramping from one set of state values to another.

In particular embodiments, a physics engine implements the algorithmsthat simulate spring movement. A number of springs may be attached to anobject. For example, if an object is pinched by a user with two fingers,two springs may be attached to the object at the positions correspondingto the fingers pinching the object. As the object moves (e.g., draggedby the user's fingers), its movement follows the paths of the springs,so that the movement of the object is animated based on the physics ofthe spring movement. In particular embodiments, the algorithm may takeinto consideration variables such as tension, mass, damping effect, thevelocity of the finger's movement, etc. As an example, if the user'sfinger moves faster, it may cause the object to bounce more. Conversely,if the user's finger moves slower, the object may bounce less. Asanother example, the springs may tighten or loosen depending on wherethe fingers touch and pinch an object. When the spring is closer to afinger, it may tighten. When the spring is further away from a finger,it may loosen. When the spring tightens (e.g., an image is more foldeddue to the user's fingers pinching the image moving closer together),there may be less movement on the part of the object. Conversely, whenthe spring loosens (e.g., an image is less folded due to the user'sfingers pinching the image moving further apart), there may be moremovement on the part of the object. In some implementations, when twofingers pinching an image move apart to unfold the image or move closeto fold the image, the edges of the image pinched by the two fingers mayfirst unfold or fold pass the fingers' positions, and then bounce andfold or unfold back to find the correction positions of the fingers, andthus the correct degree of unfolding or folding. This allows the imageto determine its folding and unfolding degrees in real time.

In particular embodiments, the movement of an object may be predictedbased on a user's intent. For example, if a user picks up an object andthen moves the fingers toward the left side of the screen, the user'sintent may be to place the object near the left side of the screen. Theobject's final position may be projected based on the direction as wellas the velocity of the user's finger movement (e.g., the position theobject may move to in 0.5 seconds time).

In particular embodiments, animation of the objects are implementedbased on the algorithms implemented in the physical engine. For example,when an object is pinched up, moved to a different position, and thenreleased, the object may bounce around a little. This is implemented asan animation sequence. The bouncing path and characteristics of themovement may be governed by the algorithms implemented in the physicsengine.

In particular embodiments, when an image is picked up, the animation ofits movements following the user's fingers may be based on springmotions. For example, how much should the image fold or unfold, how muchshould the image rotate, or how much should the image bounce against theedge of the screen, as the user's fingers move may be determined basedon spring motions. In particular embodiments, an image's movements maybe simulated by, supposedly, attaching the image to an imaginary spring.When the user's fingers pick up the image, the supposed force the user'sfingers exert on the image may cause the image to have supposed mass.When an object with mass (e.g., an image with supposed mass) is attachedto a spring, its movements may follow specific physical properties. Inaddition to the mass, the spring may have properties such as, forexample and without limitation, tension, stretch, and dampening. Byselecting various values for these properties, different movements ofthe image may be simulated.

In particular embodiments, when zooming in on an object, the objectincreases in size. When zooming out on an object, the object decreasesin size. The changing of the object's size may be depicted in ananimation sequence, where the movements of the object may be based onspring movements.

In particular embodiments, as an object moves towards its finaldestination, the intermediate positions of the object may beinterpolated based on spring movements.

Electronic Device

Particular embodiments may be implemented on one or more electronicdevices or computer systems. For example, the user interface may bedisplayed on the screen of such an electronic device. FIG. 10illustrates an example electronic device 1000. In particularembodiments, one or more computer systems 1000 perform one or more stepsof one or more methods described or illustrated herein. In particularembodiments, one or more computer systems 1000 provide functionalitydescribed or illustrated herein. In particular embodiments, softwarerunning on one or more computer systems 1000 performs one or more stepsof one or more methods described or illustrated herein or providesfunctionality described or illustrated herein. Particular embodimentsinclude one or more portions of one or more computer systems 1000.

This disclosure contemplates any suitable number of computer systems1000. This disclosure contemplates computer system 1000 taking anysuitable physical form. As example and not by way of limitation,computer system 1000 may be an embedded computer system, asystem-on-chip (SOC), a single-board computer system (SBC) (such as, forexample, a computer-on-module (COM) or system-on-module (SOM)), adesktop computer system, a laptop or notebook computer system, aninteractive kiosk, a mainframe, a mesh of computer systems, a mobiletelephone, a personal digital assistant (PDA), a server, or acombination of two or more of these. Where appropriate, computer system1000 may include one or more computer systems 1000; be unitary ordistributed; span multiple locations; span multiple machines; or residein a cloud, which may include one or more cloud components in one ormore networks. Where appropriate, one or more computer systems 1000 mayperform without substantial spatial or temporal limitation one or moresteps of one or more methods described or illustrated herein. As anexample and not by way of limitation, one or more computer systems 1000may perform in real time or in batch mode one or more steps of one ormore methods described or illustrated herein. One or more computersystems 1000 may perform at different times or at different locationsone or more steps of one or more methods described or illustratedherein, where appropriate.

In particular embodiments, computer system 1000 includes a processor1002, memory 1004, storage 1006, an input/output (I/O) interface 1008, acommunication interface 1010, and a bus 1012. Although this disclosuredescribes and illustrates a particular computer system having aparticular number of particular components in a particular arrangement,this disclosure contemplates any suitable computer system having anysuitable number of any suitable components in any suitable arrangement.

In particular embodiments, processor 1002 includes hardware forexecuting instructions, such as those making up a computer program. Asan example and not by way of limitation, to execute instructions,processor 1002 may retrieve (or fetch) the instructions from an internalregister, an internal cache, memory 1004, or storage 1006; decode andexecute them; and then write one or more results to an internalregister, an internal cache, memory 1004, or storage 1006. In particularembodiments, processor 1002 may include one or more internal caches fordata, instructions, or addresses. This disclosure contemplates processor1002 including any suitable number of any suitable internal caches,where appropriate. As an example and not by way of limitation, processor1002 may include one or more instruction caches, one or more datacaches, and one or more translation lookaside buffers (TLBs).Instructions in the instruction caches may be copies of instructions inmemory 1004 or storage 1006, and the instruction caches may speed upretrieval of those instructions by processor 1002. Data in the datacaches may be copies of data in memory 1004 or storage 1006 forinstructions executing at processor 1002 to operate on; the results ofprevious instructions executed at processor 1002 for access bysubsequent instructions executing at processor 1002 or for writing tomemory 1004 or storage 1006; or other suitable data. The data caches mayspeed up read or write operations by processor 1002. The TLBs may speedup virtual-address translation for processor 1002. In particularembodiments, processor 1002 may include one or more internal registersfor data, instructions, or addresses. This disclosure contemplatesprocessor 1002 including any suitable number of any suitable internalregisters, where appropriate. Where appropriate, processor 1002 mayinclude one or more arithmetic logic units (ALUs); be a multi-coreprocessor; or include one or more processors 1002. Although thisdisclosure describes and illustrates a particular processor, thisdisclosure contemplates any suitable processor.

In particular embodiments, memory 1004 includes main memory for storinginstructions for processor 1002 to execute or data for processor 1002 tooperate on. As an example and not by way of limitation, computer system1000 may load instructions from storage 1006 or another source (such as,for example, another computer system 1000) to memory 1004. Processor1002 may then load the instructions from memory 1004 to an internalregister or internal cache. To execute the instructions, processor 1002may retrieve the instructions from the internal register or internalcache and decode them. During or after execution of the instructions,processor 1002 may write one or more results (which may be intermediateor final results) to the internal register or internal cache. Processor1002 may then write one or more of those results to memory 1004. Inparticular embodiments, processor 1002 executes only instructions in oneor more internal registers or internal caches or in memory 1004 (asopposed to storage 1006 or elsewhere) and operates only on data in oneor more internal registers or internal caches or in memory 1004 (asopposed to storage 1006 or elsewhere). One or more memory buses (whichmay each include an address bus and a data bus) may couple processor1002 to memory 1004. Bus 1012 may include one or more memory buses, asdescribed below. In particular embodiments, one or more memorymanagement units (MMUs) reside between processor 1002 and memory 1004and facilitate accesses to memory 1004 requested by processor 1002. Inparticular embodiments, memory 1004 includes random access memory (RAM).This RAM may be volatile memory, where appropriate. Where appropriate,this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, whereappropriate, this RAM may be single-ported or multi-ported RAM. Thisdisclosure contemplates any suitable RAM. Memory 1004 may include one ormore memories 1004, where appropriate. Although this disclosuredescribes and illustrates particular memory, this disclosurecontemplates any suitable memory.

In particular embodiments, storage 1006 includes mass storage for dataor instructions. As an example and not by way of limitation, storage1006 may include an HDD, a floppy disk drive, flash memory, an opticaldisc, a magneto-optical disc, magnetic tape, or a Universal Serial Bus(USB) drive or a combination of two or more of these. Storage 1006 mayinclude removable or non-removable (or fixed) media, where appropriate.Storage 1006 may be internal or external to computer system 1000, whereappropriate. In particular embodiments, storage 1006 is non-volatile,solid-state memory. In particular embodiments, storage 1006 includesread-only memory (ROM). Where appropriate, this ROM may bemask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM),electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM),or flash memory or a combination of two or more of these. Thisdisclosure contemplates mass storage 1006 taking any suitable physicalform. Storage 1006 may include one or more storage control unitsfacilitating communication between processor 1002 and storage 1006,where appropriate. Where appropriate, storage 1006 may include one ormore storages 1006. Although this disclosure describes and illustratesparticular storage, this disclosure contemplates any suitable storage.

In particular embodiments, I/O interface 1008 includes hardware,software, or both providing one or more interfaces for communicationbetween computer system 1000 and one or more I/O devices. Computersystem 1000 may include one or more of these I/O devices, whereappropriate. One or more of these I/O devices may enable communicationbetween a person and computer system 1000. As an example and not by wayof limitation, an I/O device may include a keyboard, keypad, microphone,monitor, mouse, printer, scanner, speaker, still camera, stylus, tablet,touch screen, trackball, video camera, another suitable I/O device or acombination of two or more of these. An I/O device may include one ormore sensors. This disclosure contemplates any suitable I/O devices andany suitable I/O interfaces 1008 for them. Where appropriate, I/Ointerface 1008 may include one or more device or software driversenabling processor 1002 to drive one or more of these I/O devices. I/Ointerface 1008 may include one or more I/O interfaces 1008, whereappropriate. Although this disclosure describes and illustrates aparticular I/O interface, this disclosure contemplates any suitable I/Ointerface.

In particular embodiments, communication interface 1010 includeshardware, software, or both providing one or more interfaces forcommunication (such as, for example, packet-based communication) betweencomputer system 1000 and one or more other computer systems 1000 or oneor more networks. As an example and not by way of limitation,communication interface 1010 may include a network interface controller(NIC) or network adapter for communicating with an Ethernet or otherwire-based network or a wireless NIC (WNIC) or wireless adapter forcommunicating with a wireless network, such as a WI-FI network. Thisdisclosure contemplates any suitable network and any suitablecommunication interface 1010 for it. As an example and not by way oflimitation, computer system 1000 may communicate with an ad hoc network,a personal area network (PAN), a local area network (LAN), a wide areanetwork (WAN), a metropolitan area network (MAN), or one or moreportions of the Internet or a combination of two or more of these. Oneor more portions of one or more of these networks may be wired orwireless. As an example, computer system 1000 may communicate with awireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN), a WI-FInetwork, a WI-MAX network, a cellular telephone network (such as, forexample, a Global System for Mobile Communications (GSM) network), orother suitable wireless network or a combination of two or more ofthese. Computer system 1000 may include any suitable communicationinterface 1010 for any of these networks, where appropriate.Communication interface 1010 may include one or more communicationinterfaces 1010, where appropriate. Although this disclosure describesand illustrates a particular communication interface, this disclosurecontemplates any suitable communication interface.

In particular embodiments, bus 1012 includes hardware, software, or bothcoupling components of computer system 1000 to each other. As an exampleand not by way of limitation, bus 1012 may include an AcceleratedGraphics Port (AGP) or other graphics bus, an Enhanced Industry StandardArchitecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT)interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBANDinterconnect, a low-pin-count (LPC) bus, a memory bus, a Micro ChannelArchitecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, aPCI-Express (PCIe) bus, a serial advanced technology attachment (SATA)bus, a Video Electronics Standards Association local (VLB) bus, oranother suitable bus or a combination of two or more of these. Bus 1012may include one or more buses 1012, where appropriate. Although thisdisclosure describes and illustrates a particular bus, this disclosurecontemplates any suitable bus or interconnect.

Herein, a computer-readable non-transitory storage medium or media mayinclude one or more semiconductor-based or other integrated circuits(ICs) (such, as for example, field-programmable gate arrays (FPGAs) orapplication-specific ICs (ASICs)), hard disk drives (HDDs), hybrid harddrives (HHDs), optical discs, optical disc drives (ODDs),magneto-optical discs, magneto-optical drives, floppy diskettes, floppydisk drives (FDDs), magnetic tapes, solid-state drives (SSDs),RAM-drives, SECURE DIGITAL cards or drives, any other suitablecomputer-readable non-transitory storage medium or media, or anysuitable combination of two or more of these, where appropriate. Acomputer-readable non-transitory storage medium or media may bevolatile, non-volatile, or a combination of volatile and non-volatile,where appropriate.

Herein, “or” is inclusive and not exclusive, unless expressly indicatedotherwise or indicated otherwise by context. Therefore, herein, “A or B”means “A, B, or both,” unless expressly indicated otherwise or indicatedotherwise by context. Moreover, “and” is both joint and several, unlessexpressly indicated otherwise or indicated otherwise by context.Therefore, herein, “A and B” means “A and B, jointly or severally,”unless expressly indicated otherwise or indicated otherwise by context.

This disclosure encompasses all changes, substitutions, variations,alterations, and modifications to the example embodiments herein that aperson having ordinary skill in the art would comprehend. Moreover,reference in the appended claims to an apparatus or system or acomponent of an apparatus or system being adapted to, arranged to,capable of, configured to, enabled to, operable to, or operative toperform a particular function encompasses that apparatus, system,component, whether or not it or that particular function is activated,turned on, or unlocked, as long as that apparatus, system, or componentis so adapted, arranged, capable, configured, enabled, operable, oroperative.

What is claimed is:
 1. A computer-implemented method comprising:loading, into a memory of a user device, at least a first set of aplurality of objects in a hierarchy upon opening of the first set of theobjects, the hierarchy having one or more layers and each layer havingat least one of the objects, wherein the loaded objects comprise a firstset of parent objects and, for at least one of the parent objects, a setof child objects associated with the parent object in the hierarchy,wherein the first set of parent objects comprises a table of contentssection that comprises a plurality of thumbnails, and wherein the tableof contents section and the corresponding thumbnails are loaded into thememory of the user device; displaying a subset of the loaded objects ona screen of the user device, the displayed objects comprising: at leastone parent object of the first set of parent objects, wherein the loadedparent objects are successively presented in a sequence when scrollinginput is received with respect to the displayed parent objects; and oneor more child objects, each of the displayed child objects beingassociated with one of the displayed parent objects; and in response toreceiving the scrolling input with respect to the displayed parentobjects, preloading a second set of a plurality of objects in thehierarchy different from the first set of the plurality of objects to bedisplayed after the displayed subset of loaded objects based on theacceleration of the received scrolling input through the sequence ofparent objects such that when the acceleration of the received scrollinginput is less than or equal to a predetermined acceleration, thepreloading of the second set of the plurality of objects includespreloading and storing one or more child objects associated with atleast one of the loaded parent objects; and when the acceleration of thereceived scrolling input is more than the predetermined acceleration,the preloading of the second set of the plurality of objects includespreloading and storing a second set of parent objects different from thefirst set of parent objects and concurrently preloading and storing oneor more child objects associated with at least one parent object of thesecond set of parent objects.
 2. The computer-implemented method ofclaim 1, wherein: the user scrolls through the displayed parent objectsby swiping across the screen of the user device; and the acceleration ofthe user scrolling is determined based on a speed the user swipes acrossthe screen of the user device.
 3. The computer-implemented method ofclaim 1, wherein when the user scrolls through the displayed parentobjects at the acceleration that is greater than the predeterminedacceleration, the second set of the plurality of objects in thehierarchy are further, in position, from the displayed parent objectscurrently displayed on the screen of the user device.
 4. Thecomputer-implemented method of claim 1, wherein when the user scrollsthrough the displayed parent objects at the acceleration that is lessthan or equal to the predetermined acceleration, the second set of theplurality of objects in the hierarchy are closer, in position, to thedisplayed parent objects currently displayed on the screen of the userdevice.
 5. The computer-implemented method of claim 1, whereinpreloading the child objects associated with at least one of the loadedparent objects comprises downloading the child objects from a remotedevice to the user device.
 6. The computer-implemented method of claim1, wherein preloading the child objects associated with at least one ofthe loaded parent objects comprises rendering the child objects fordisplay.
 7. The computer-implemented method of claim 1, wherein eachparent object is a photo album and each child object is a photobelonging to a specific photo album.
 8. The computer-implemented methodof claim 1, wherein each parent object is a section of a digital bookand each child object is a page belonging to a specific section.
 9. Oneor more computer-readable non-transitory storage media embodyingsoftware that is operable when executed to: load, into a memory of auser device, at least a first set of a plurality of objects in ahierarchy upon opening of the first set of the objects, the hierarchyhaving one or more layers and each layer having at least one of theobjects, wherein the loaded objects comprise a first set of parentobjects and, for at least one of the parent objects, a set of childobjects associated with the parent object in the hierarchy, wherein thefirst set of parent objects comprises a table of contents section thatcomprises a plurality of thumbnails, and wherein the table of contentssection and the corresponding thumbnails are loaded into the memory ofthe user device; display a subset of the loaded objects on a screen ofthe user device, the displayed objects comprising: at least one parentobject of the first set of parent objects, wherein the loaded parentobjects are successively presented in a sequence when scrolling input isreceived with respect to the displayed parent objects; and one or morechild objects, each of the displayed child objects being associated withone of the displayed parent objects; and in response to receiving thescrolling input with respect to the displayed parent objects, preloadinga second set of a plurality of objects in the hierarchy different fromthe first set of the plurality of objects to be displayed after thedisplayed subset of loaded objects based on the acceleration of thereceived scrolling input through the sequence of parent objects suchthat when the acceleration of the received scrolling input is less thanor equal to a predetermined acceleration, the preloading of the secondset of the plurality of objects includes preloading and storing one ormore child objects associated with at least one of the loaded parentobjects; and when the acceleration of the received scrolling input ismore than the predetermined acceleration, the preloading of the secondset of the plurality of objects includes preloading and storing a secondset of parent objects different from the first set of parent objects andconcurrently preloading and storing one or more child objects associatedwith at least one parent object of the second set of parent objects. 10.The media of claim 9, wherein: the user scrolls through the displayedparent objects by swiping across the screen of the user device; and theacceleration of the user scrolling is determined based on a speed theuser swipes across the screen of the user device.
 11. The media of claim9, wherein when the user scrolls through the displayed parent objects atthe acceleration that is greater than the predetermined acceleration,the second set of the plurality of objects in the hierarchy are further,in position, from the displayed parent objects currently displayed onthe screen of the user device.
 12. The media of claim 9, wherein whenthe user scrolls through the displayed parent objects at theacceleration that is less than or equal to the predeterminedacceleration, the second set of the plurality of objects in thehierarchy are closer, in position, to the displayed parent objectscurrently displayed on the screen of the user device.
 13. The media ofclaim 9, wherein preload the child objects associated with at least oneof the loaded parent objects comprises download the child objects from aremote device to the user device.
 14. The media of claim 9, whereinpreload the child objects associated with at least one of the loadedparent objects comprises render the child objects for display.
 15. Asystem comprising: one or more processors; and a memory coupled to theprocessors comprising instructions executable by the processors, theprocessors operable when executing the instructions to: load, into amemory of a user device, at least a first set of a plurality of objectsin a hierarchy upon opening of the first set of the objects, thehierarchy having one or more layers and each layer having at least oneof the objects, wherein the loaded objects comprise a first set ofparent objects and, for at least one of the parent objects, a set ofchild objects associated with the parent object in the hierarchy,wherein the first set of parent objects comprises a table of contentssection that comprises a plurality of thumbnails, and wherein the tableof contents section and the corresponding thumbnails are loaded into thememory of the user device; display a subset of the loaded objects on ascreen of the user device, the displayed objects comprising: at leastone parent object of the first set of parent objects, wherein the loadedparent objects are successively presented in a sequence when scrollinginput is received with respect to the displayed parent objects; and; oneor more child objects, each of the displayed child objects beingassociated with one of the displayed parent objects; and in response toreceiving the scrolling input with respect to the displayed parentobjects, preloading a second set of a plurality of objects in thehierarchy different from the first set of the plurality of objects to bedisplayed after the displayed subset of loaded objects based on theacceleration of the received scrolling input through the sequence ofparent objects such that when the acceleration of the received scrollinginput is less than or equal to a predetermined acceleration, thepreloading of the second set of the plurality of objects includespreloading and storing one or more child objects associated with atleast one of the loaded parent objects; and when the acceleration of thereceived scrolling input is more than the predetermined acceleration,the preloading of the second set of the plurality of objects includespreloading and storing a second set of parent objects different from thefirst set of parent objects and concurrently preloading and storing oneor more child objects associated with at least one parent object of thesecond set of parent objects.
 16. The system of claim 15, wherein: theuser scrolls through the displayed parent objects by swiping across thescreen of the user device; and the acceleration of the user scrolling isdetermined based on a speed the user swipes across the screen of theuser device.
 17. The system of claim 15, wherein when the user scrollsthrough the displayed parent objects at the acceleration that is greaterthan the predetermined acceleration, the second set of the plurality ofobjects in the hierarchy are further, in position, from the displayedparent objects currently displayed on the screen of the user device. 18.The system of claim 15, wherein when the user scrolls through thedisplayed parent objects at the acceleration that is less than or equalto the predetermined acceleration, the second set of the plurality ofobjects in the hierarchy are closer, in position, to the displayedparent objects currently displayed on the screen of the user device. 19.The system of claim 15, wherein preload the child objects associatedwith at least one of the loaded parent objects comprises download thechild objects from a remote device to the user device.
 20. The system ofclaim 15, wherein preload the child objects associated with at least oneof the loaded parent objects comprises render the child objects fordisplay.